Internet Info 1994 March

home *** CD-ROM | disk | FTP | other *** search

/ Internet Info 1994 March / Internet Info CD-ROM (Walnut Creek) (March 1994).iso / inet / internet-drafts / draft-ietf-atommib-atm-01.txt < prev next >

Wrap

Text File | 1993-10-21 | 115.3 KB | 3,187 lines

Internet Draft ATM Management Objects October 19, 1993 Definitions of Managed Objects for ATM Management Version 2.0 October 19, 1993 Masuma Ahmed (editor) Kaj Tesink (editor) Bell Communications Research 331 Newman Springs Road Red Bank, NJ 07701 mxa@mail.bellcore.com kaj@cc.bellcore.com 1. Status of this Memo This document is an Internet Draft. Internet Drafts are working documents of the Internet Engineering Task Force (IETF), its Areas, and its Working Groups. Note that other groups may also distribute working documents as Internet Drafts. Internet Drafts are valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet Drafts as reference material or to cite them other than as a "working draft" or "work in progress". Please check the I-D abstract listing contained in each Internet Draft directory to learn the current status of this or any other Internet Draft. Distribution of this document is unlimited. Masuma Ahmed and Kaj Tesink (editors) Expires 4/19/94 [Page 1] Internet Draft ATM Management Objects October 19, 1993 2. Abstract This memo defines an experimental portion of the Management Information Base (MIB) for use with network management protocols in TCP/IP-based internets. In particular, it defines objects for managing ATM-based interfaces, networks and services. This memo specifies a MIB module in a manner that is both compliant to the SNMPv2 SMI, and semantically identical to the peer SNMPv1 definitions. [Temporary Note: Upon progression of this specification as a Proposed Standard, an SNMPv2 and an SNMPv1 version of this MIB module will be made available to ease migration.] This memo does not specify a standard for the Internet community. 3. Change Log This section tracks changes made to the revisions of the Internet Drafts of this document. It will be deleted when the document is published as an RFC. The following changes were made for the version of the document dated August 9, 1993. - Representation of the ATM layer in the Interface Group has been modified as follows: The ATM layer objects are now represented using the fixedLengthGroup in the ifTable. The objects supported are ifIndex, ifDescr, ifType, ifSpeed, ifPhyAddress, ifAdminStatus, ifOperStatus, ifLastChange, ifInOctets, ifInErrors, ifInUnknownProtos, ifSpecific, ifName, ifLinkUpDownTrapEnable, ifHighSpeed, ifHCInOctets, and ifHCOutOctets. The ifPacketGroup does not apply to ATM layer. - The performance parameter group per virtual link has been removed. - The object atmInterfaceSpecific has been deleted from the atmInterfaceConfTable. - There was an error in the atmInterfaceTrafficEnforcementTypes Masuma Ahmed and Kaj Tesink (editors) Expires 4/19/94 [Page 2] Internet Draft ATM Management Objects October 19, 1993 which was corrected. - AAL3/4 and AAL5 are now represented as separate entries in the ifTable. The value of the ifType for AAL3/4 Common Part Convergence Sublayer (CPCS) is the ifType of the SMDS Interface Protocol (SIP). The AAL3/4 CPCS layer objects are represented using the SIP MIB, RFC 1304. - The value of the ifType for AAL5 is 49. The representation of AAL5 using ifTable and in the ATM MIB is currently under study and will be included in the future. - The SONET Transmission Convergence (TC) sublayer is renamed as TC sublayer. This is because TC sublayer can be used for carrying ATM directly over SONET as well as directly over DS3 or DS1 physical layers. The following changes were made for the version of the document dated July 15, 1993. - This MIB module is made compliant with SNMPv2 SMI. - This MIB module incorporates the changes agreed upon at the AToM MIB WG meeting in Amsterdam. - The objects atmInterfacePortIdentifier, atmInterfaceTransmissionType and atmInterfaceMediaType have been deleted from the atmInterfaceConfTable. The object atmInterfaceIlmiVpiVci has been clarified. - Entries in the ifTable have been updated for ATM interface, and AAL level interfaces. - Representations of the AAL level interfaces in the Interface Group have been modified as follows: The AAL level is now represented per ATM interface and not per virtual connection. Therefore, the AAL pointer group is deleted. AAL3/4 and AAL5 CPCS layers are now combined and represented as a single entry in the Interface Group. Masuma Ahmed and Kaj Tesink (editors) Expires 4/19/94 [Page 3] Internet Draft ATM Management Objects October 19, 1993 AAl1 SAR layer is also now represented in the Interface Group. - Formal conformance statements have beed added. 4. The SNMPv2 Network Management Framework The SNMPv2 Network Management Framework consists of four major components. They are: RFC 1442 which defines the SMI, the mechanisms used for describing and naming objects for the purpose of management. RFC 1213 defines MIB-II, the core set of managed objects for the Internet suite of protocols. RFC 1445 which defines the administrative and other architectural aspects of the framework. RFC 1448 which defines the protocol used for network access to managed objects. The Framework permits new objects to be defined for the purpose of experimentation and evaluation. Masuma Ahmed and Kaj Tesink (editors) Expires 4/19/94 [Page 4] Internet Draft ATM Management Objects October 19, 1993 5. Objects Managed objects are accessed via a virtual information store, termed the Management Information Base or MIB. Objects in the MIB are defined using the subset of Abstract Syntax Notation One (ASN.1) [3] defined in the SMI. In particular, each object has a name, a syntax, and an encoding. The name is an OBJECT IDENTIFIER, an administratively assigned name, which specifies an object type. The object type together with an object instance serves to uniquely identify a specific instantiation of the object. For human convenience, we often use a textual string, termed the descriptor, to also refer to the object type. The syntax of an object type defines the abstract data structure corresponding to that object type. The ASN.1 language is used for this purpose. However, the SMI RFC 1442 purposely restricts the ASN.1 constructs which may be used. These restrictions are explicitly made for simplicity. The encoding of an object type is simply how that object type is represented using the object type's syntax. Implicitly tied to the notion of an object type's syntax and encoding is how the object type is represented when being transmitted on the network. The SMI specifies the use of the basic encoding rules of ASN.1 [4], subject to the additional requirements imposed by the SNMPv2. 5.1. Format of Definitions Section 9 contains the specification of all object types contained in this MIB module. The object types are defined using the conventions defined in the SNMPv2 SMI. Masuma Ahmed and Kaj Tesink (editors) Expires 4/19/94 [Page 5] Internet Draft ATM Management Objects October 19, 1993 6. ATM Terminology Some basic ATM terminologies are described in this section to facilitate defining the ATM managed objects and ATM management groups. 6.1. VCL/VPL and VCC/VPC There are two distinct types of ATM virtual connections: Virtual Channel Connections (VCCs) and Virtual Path Connection (VPCs). As shown in the figures below, ATM virtual connections are made of virtual links such as Virtual Channel Links (VCLs) or Virtual Path Links (VPLs). The VCI/VPI or VPI field in the ATM cell header associates each cell with a particular VCL or VPL over a given physical link. <-----------------------VCC-------------------------------> ---------- ---------- | ATM | | ATM | | | | | O<------->|Switch |<-------------->|Switch |<------------>O VCL1 | | VCL2 | | VCL3 ---------- ---------- <---a managed segment--> <------------------a managed segment-----------------------> Figure 1: Virtual Channel Links and Virtual Channel Connection As shown in Figure 1, end-to-end VCCs are created by the concatenation of VCLs. This is a path composed of more than once VCL spanning multiple network nodes to form a connection between two end-points. The VCLs used to form a VCC all have the same traffic characteristics (i.e., bandwidth parameters, QoS Class parameters, etc.). The switch routes cells between VCLs, thereby, forming VCCs across the network. The VCCs are bi-directional by definition. However, the traffic parameters in two directions of the connection can be symmetric or asymmetric, i.e., the two directions of the virtual connection can have the same or different traffic flows. Therefore, a uni-directional traffic flow across a VCC is achieved by assigning a zero bandwidth in one direction. Masuma Ahmed and Kaj Tesink (editors) Expires 4/19/94 [Page 6] Internet Draft ATM Management Objects October 19, 1993 An ATM equipment (e.g., a router, switch or network) typically does not support a VCC end-to-end, but only a segment of the VCC (see Figure 1). Therefore, the managed resource is typically a VCC segment and the management of an end-to-end VCC is achieved by appropriate management of its individual components. Many VCLs may be carried within a single VPL. All VCLs within a single VPL share the same VPI value in the ATM header. In turn, several VPLs can be carried over a single physical link. <-----------------------VPC-----------------------------> ---------- ---------- | ATM | | ATM | VCCs | | | | <--|---------|Switch |----------------|Switch |----------|--> <--| | | | | |--> <--|---------| |----------------| |----------|--> VPL1 ---------- VPL2 ---------- VPL3 <---------a managed segment---------> <-------------------a managed segment-------------------> Figure 2: Virtual Path Links and Virtual Path Connection End-to-end VPCs are created by the concatenation of VPLs and may be viewed as a logical bundle of VCCs as shown in Figure 2. An end-to-end VPC may be used by a user to group all those VCCs going to the same destination. The switch switches VPLs while ignoring the VCLs within it. Thus, at the switching point, a translation is performed on the VPL identifier fields (i.e., the VPI) in the ATM cell header. The VPI field does not have end-to-end significance over the entire VPC. Note that, for a switch or network supporting a VPC, only the VCI value has end-to-end significance since the switch or the network does not process the VCI field. Therefore, in the context of a given switch or network, VPC and VCC are non- overlapping virtual connections. A switch or network typically does not support a VPC end-to- end, but only a segment of the VPC (see Figure 2). Therefore, in a switch or network, a managed resource is typically a VPC Masuma Ahmed and Kaj Tesink (editors) Expires 4/19/94 [Page 7] Internet Draft ATM Management Objects October 19, 1993 segment and the management of an end-to-end VPC is achieved by appropriate management of its individual components. 6.2. PVC and SVC A Permanent Virtual Connection (PVC) is a provisioned VCC or VPC. A Switched Virtual Connection (SVC) is a switched VCC or VPC that is set up in real-time via call set-up signaling procedures. A PVC (or an SVC) can be a point-to-point, point-to-multipoint, or multipoint-to-multipoint VCC or VPC. 6.3. Traffic Management Parameters 6.3.1. Traffic Policing and Traffic Shaping Parameters In order to allocate resources fairly among different users, it is usually necessary to police traffic at different resource access points. The traffic enforcement or policing taken at a UNI is called Usage Parameter Control (UPC) and is activated on an incoming VCL or VPL as shown in Figure 3. The use of the traffic enforcer at the ingress of the connection is to make sure that the user traffic does not exceed the negotiated traffic parameters such as the peak cell rate. ---------- ---------- UNI | ATM | NNI | ATM | UNI | | switch | | | switch | | O<---|---->X(UPC) |<-------|--------->| (UPC)X<------|--->O | VCL | | | VCL | | VCL | ---------- ---------- Figure 3: An Example of a UPC In addition, traffic shaping may be performed on an outgoing VPL or VCL at a given ATM interface. The function of the ATM traffic shaper at the egress of the connection is to smooth the outgoing cell traffic inter-arrival time. If policing or shaping is not performed then the policing or shaping parameters are zero. Masuma Ahmed and Kaj Tesink (editors) Expires 4/19/94 [Page 8] Internet Draft ATM Management Objects October 19, 1993 6.3.2. Cell Loss Priority To prioritize traffic during resource congestion, ATM cells are assigned one of the two types of Cell Loss Priority (CLP), CLP=0 and CLP=1. ATM cells with CLP=0 are treated as higher priority traffic than ATM cells with CLP=1. 6.3.3. QoS Class A VCC or VPC is associated with one of a number of Quality of Service (QoS) classes. Four QoS classes have been specified to support service class A (constant bit rate video and circuit emulation), service class B (variable bit rate video/audio), service class C (connection-oriented data) and service class D (connectionless data). The VCLs (or VPLs) concatenated to form a VCC (or VPC) will all have the same QoS class as that of the VCC (or VPC). Note that, the cell loss ratio, Cell Delay Variation (CDV), and end-to-end cell delay parameters are defined as part of QoS Class definition. 7. Overview ATM management objects are used to manage ATM interfaces and ATM virtual connection segments supported by a switch, host, or network. This section provides an overview and background of how to use this MIB and other potential MIBs for this purpose. The purpose of this memo is primarily to manage ATM PVCs. Management of ATM SVCs may require additional capabilities which are currently outside the scope of this memo. 7.1. Background The ATM MIB shall be used for ATM Customer Network Management (CNM) and ATM Network Management (NM) purposes for managing ATM interfaces and ATM virtual connections. Anything inside a switch or network is invisible and therefore shall not be manageable by the ATM MIB. The ATM MIB shall support configuration, fault, and performance management of: (1) ATM interfaces Masuma Ahmed and Kaj Tesink (editors) Expires 4/19/94 [Page 9] Internet Draft ATM Management Objects October 19, 1993 (2) ATM virtual connections In addition, other MIB modules are necessary to manage ATM interfaces and connections. Examples include MIB II for general system and interface management, the DS3 or SONET MIBs for management of physical interfaces, and, as appropriate, MIB modules for applications that make use of ATM, such as SMDS. These MIB modules are outside the scope of this specification. The current specification of this ATM MIB is based on SNMPv2. 7.2. Structure of the MIB The managed ATM objects are arranged into the following groups for management of (1) ATM local interfaces and (2) ATM virtual connections. For a switch or network that terminates or originates VCCs, the management of ATM local interfaces also includes management of ATM adaptation layers for ATM applications. In addition, managed ATM objects for activation/deactivation of OAM cell flows and ATM traps notifying virtual connection or virtual link failures such as VP-AIS may be needed and are under study. (1) ATM interface configuration group (2) ATM interface DS3 PLCP group (3) ATM interface TC Sublayer group (4) ATM Virtual Connection Segment (VPC/VCC) groups The groups listed above are the basic units of conformance. If the semantics of a group are applicable to an implementation, then it must implement all objects in that group. For example, a managed agent must implement the VCC group if and only if it manages the VCCs. 7.3. ATM Interface Configuration Group This group is designed to manage ATM cell layer configuration of local ATM interfaces on an ATM device. In addition, this group provides pointers to any additional MIB modules (e.g., enterprise-specific) that may be needed to manage this interface. Masuma Ahmed and Kaj Tesink (editors) Expires 4/19/94[Page 10] Internet Draft ATM Management Objects October 19, 1993 7.4. ATM Interface DS3 PLCP and TC Layer Groups These groups provide performance statistics of the DS3 PLCP and TC sublayer of local ATM interfaces on a managed ATM device. DS3 PLCP and TC sublayer are currently used to carry ATM cells respectively over DS3 and SONET transmission paths. 7.5. ATM Virtual Connection Segment Groups 7.5.1. Introduction In these groups, managed segments of virtual connections are modeled as a set of unidirectional traffic flows between an ingress and an egress of a switch or network (see Figure 4). This allows for independent treatment of the forward and backward traffic flows of virtual connections, and allows for the management of all possible topologies (pt/pt, pt/mpt, mpt/mpt). Masuma Ahmed and Kaj Tesink (editors) Expires 4/19/94[Page 11] Internet Draft ATM Management Objects October 19, 1993 Managed Resource Managed Resource Ingress___________________________________Egress _________________| >> Virtual Connection traffic >> |______________ |__________________________________| Figure 4 - Model unidirectional traffic flow The In and Out in this model necessarily differs from the model in the ifTable of MIB II, where the In/Out is measured at the same port. The relationship is shown in Figure 5. Port x __________________________/ LocalIn--> (Ingress XtoY)| >> XtoY traffic >> / ____________________________| ________________________/ LocalOut<-- (Egress YtoX)| << YtoX traffic << / |________________________/ Figure 5 - Relation Local In/Out with Virtual Connection Ingress/Egress Each Ingress-Egress flow is represented as a separate entry in the atmConnectionTables. This approach accommodates unidirectional, bidirectional, point-to-point, point-to- multipoint, and multipoint-to-multipoint topologies. It also allows for efficient searching by port number. For example, a bidirectional point-to-point virtual connection between port 1 and port 2 is represented by the entries: {Port1VCx-Port2VCy} {Port2VCy-Port1VCx} Similarly, a bidirectional point-to-multipoint virtual connection from port 1 to ports 2 and 3, is represented by the entries: {Port1VCx-Port2VCy} {Port1VCx-Port3VCz} {Port2VCy-Port1VCx} {Port3VCz-Port1VCx} A bidirectional multipoint-to-multipoint virtual connection between ports 1, 2, and 3 is represented by the entries: {Port1VCx-Port2VCy} Masuma Ahmed and Kaj Tesink (editors) Expires 4/19/94[Page 12] Internet Draft ATM Management Objects October 19, 1993 {Port1VCx-Port3VCz} {Port2VCy-Port1VCx} {Port2VCy-Port3VCz} {Port3VCz-Port1VCx} {Port3VCz-Port2VCy} A unidirectional multicast from port 1 to ports 2, 3, and 4 ports 1, 2, and 3 is represented by the entries: {Port1VCx-Port2VCy} {Port1VCx-Port3VCz} {Port1VCx-Port4VCw} The purpose of atmConnectionTable is to specify for each managed virtual connection segment supported by the ATM equipment (e.g., a router, switch or network): 1) Its identifier at the ingress 2) Its identifier at the egress 3) The characterization of the virtual connection. 7.5.2. Virtual Connection Identifiers at Ingress and Egress The virtual connection identifiers at ingress and egress of the ATM equipment must be locally unique to the equipment. For VCCs, this is achieved by the tuples: {atmVCConnectionIngressPort, atmVCConnectionIngressVpi, atmVCConnectionIngressVci}, and {atmVCConnectionEgressPort, atmVCConnectionEgressVpi, atmVCConnectionEgressVci} For VPCs, this is achieved by the tuples: {atmVCConnectionIngressPort, atmVCConnectionIngressVpi}, and {atmVCConnectionEgressPort, atmVCConnectionEgressVpi} 7.5.3. Virtual Connection Characterization A virtual connection segment is characterized by the following parameters: Status: status of the virtual connection segment, Quality of Service (QoS): specifying performance objectives for the virtual connection segment, Traffic policer: specifying the traffic enforcement policy at the ingress of the virtual connection segment, and Masuma Ahmed and Kaj Tesink (editors) Expires 4/19/94[Page 13] Internet Draft ATM Management Objects October 19, 1993 Traffic shaper: specifying the traffic enforcement policy at the egress of the virtual connection segment. 7.5.4. Sets Requests for new virtual connections, discontinuation of existing virtual connections, and modifications of existing virtual connections are accommodated by proper use of the atmConnectionTableEntryStatus column. The structure of the atmConnectionTableEntry allows to request and fully qualify new connections by a single set operation. The status column follows the textual convention RowStatus defined in [RFC1443]. [Needs text specifying its use under SNMPv1]. Not all managed resources may support sets for this table. Furthermore, sets on the individual columns are only supported within the range of values, supported by the ATM equipment. The set capability shall only be supported for PVCs. SVCs are set up via appropriate call signaling procedures. The creation of one or more rows in this table has the following effects: - A virtual connection of the specified type, and with the specified qualifications shall be provisioned, - Associated entries in the local interface tables shall be created. The following constraints apply to virtual connection modifications: [text to be provided. there are probably cases where one cannot do certain modifications. For example, can one change a unidirectional PVC to a bidirectional one? Can one change the QoS of an existing virtual connection? And so on.] For some ATM equipments, requests for changes in the virtual connection table may be honored after a period of time, due to provisioning activities. SNMPv2 provides the means to accommodate it [RFC1441-1452]. However, management under SNMPv1 does not accommodate these needs. Masuma Ahmed and Kaj Tesink (editors) Expires 4/19/94[Page 14] Internet Draft ATM Management Objects October 19, 1993 7.5.5. Virtual Connection Association with Interface Addresses Interface addresses may not be typically freely allocated, and are usually assigned by the provider of the switch or network (e.g., the public service provider in case of a public network). Furthermore, addresses may be assigned without virtual connections being established. Therefore, these addresses appear in the local interface tables, and not in the atmConnectionTable. 7.5.6. Management of an End-to-End Virtual Connection [to be supplied - text explaining that one needs to figure out which switches or networks/managed VC segments take part in the virtual connection, and that one needs to string the virtual connection table info of each of those segments together if one wants to know the whole story] 8. Application of MIB II to ATM 8.1. The System Group This specifies how the System Group defined in MIB II shall be used for ATM agent/proxy agent. For ATM switches or ATM networks, the sysServices object in the System Group has the value "2" which implies that the ATM switch, host or network is providing a subnetwork level service. 8.2. The Interface Group This specifies how the Interfaces Group defined in MIB II shall be used for the management of ATM based interfaces, and in conjunction with the ATM MIB modules. This memo assumes the interpretation of the Interfaces group to be in accordance with [5] which states that the interfaces table (ifTable) contains information on the managed resource's interfaces and each sub-layer below the internetwork layer of a network interface is considered an interface. Thus, the ifTable allows the following ATM-based interfaces to be represented as table entries: Masuma Ahmed and Kaj Tesink (editors) Expires 4/19/94[Page 15] Internet Draft ATM Management Objects October 19, 1993 - ATM cell level interfaces in the ATM equipments (e.g., switches, hosts, routers or networks) with ATM interfaces. This level is concerned with generic cell counts and not with individual virtual connections. In accordance with the guidelines of ifTable, cell counts per virtual connection are not covered by ifTable, and is considered interface specific. In order to interrelate the ifEntries properly, the Interfaces Stack Group defined in [5] shall be supported. 8.2.1. Support of the ATM Cell Layer by ifTable Some specific interpretations of ifTable for the ATM cell layer follow. Object Use for the generic ATM layer. ifIndex Each ATM port is represented by an ifEntry. ifDescr Description of the ATM interface. ifType The value that is allocated for ATM is 37. ifSpeed The total bandwidth in bits per second for use by the ATM layer. ifPhysAddress The address for this interface. If an interface has multiple addresses, then this is its primary address. If an interface has no addresses, then this is an octet string of zero length. ifAdminStatus See [5]. ifOperStatus Assumes the value down(2) if the ATM cell layer or any layer below that layer is down. ifLastChange See [5]. ifInOctets The number of received octets over the interface, i.e., the number of received, assigned cells multiplied by 53. ifOutOctets The number of transmitted octets over the interface, i.e., the number of transmitted, assigned cells multiplied by 53. ifInErrors The number of cells dropped due to uncorrectable HEC errors. ifInUnknownProtos The number of received cells discarded during cell header validation, including cells with unrecognized VPI/VCI values, and cells with invalid cell header patterns. If cells with undefined PTI values are discarded, Masuma Ahmed and Kaj Tesink (editors) Expires 4/19/94[Page 16] Internet Draft ATM Management Objects October 19, 1993 they are also counted here. ifOutErrors See [5]. For implementation strategies in which no output errors can occur at the ATM layer, this will always be 0." ifSpecific Set to the OBJECT IDENTIFIER { experimental 41 }. [Ed.note to be changed to { transmission 37 } when this specification is put on the IETF standards track] ifName Textual name of the interface or an octet string of zero length. ifLinkUpDownTrapEnable Default is disabled (2). ifHighSpeed See [5]; supported if required by the compliance statements in [5]. ifHCInOctets The 64-bit version of ifInOctets; supported if required by the compliance statements in [5]. ifHCOutOctets The 64-bit version of ifOutOctets; supported if required by the compliance statements in [5]. 8.2.2. Support of the AAL3/4 by RFC 1304 The AAL3/4 CPCS layer is represented using the SMDS Interface Protocol (SIP) L3 table in the SIP MIB, RFC1304. For the management of AAL3/4 CPCS layer, all objects in the SIP L3 table are supported. 8.2.3. Support of the AAL5 by ifTable and the ATM MIB To be provided. 9. ILMI MIB and The ATM Managed Objects The ILMI MIB is specified by the ATM Forum in UNI specification document [11], to manage local ATM UNIs. The support of the ATM management functions by the ILMI MIB and the ATM MIB are compared in Table 1. In the table below, "yes" in ILMI column indicates that the management functions are supported by the ILMI MIB. The MIB groups in the ATM MIB column are the groups listed in Section 6.2. Masuma Ahmed and Kaj Tesink (editors) Expires 4/19/94[Page 17] Internet Draft ATM Management Objects October 19, 1993 Table 1 - Structuring of ATM Managed Objects ______________________________________________________________________ | | | | ATM Mgmt.Inf. |ATM Managed Objects |This memo |ILMI MIB| ______________|_________________________________|___________|________| Local Interface Information: _____________________________________________________________________ ATM interface:| (1) port identifier | ATM | | physical layer| (2) physical transmission types | MIB gr.1* |yes | configuration | (3) operational status | MIB II | | | (4) administrative status | | | _____________________________________________________________________ ATM interface:| (1) active VPI/VCI fields | ATM | | cell layer | (2) maximum number of VPCs/VCCs | MIB gr.1 |yes | configuration | (3) configured VPCs/VCCs | | | | (4) ILMI VPI/VCI value | | | | (5) additional MIB pointer | | | _____________________________________________________________________ ATM interface:|(1) received/transmitted cells | | | cell layer |(2) errored cells | MIB II |yes | performance |(3) header content violations | | | _____________________________________________________________________ ATM interface:|(1)DS3 PLCP severely errored | ATM | | PLCP & TC | framing seconds | MIB gr.2,3| | layer |(2)DS3 PLCP unavailable seconds | |no | performance |(3)DS3 PLCP alarm state | | | |(4)out of cell delineation events| | | |(5)TC alarm state | | | _____________________________________________________________________ Masuma Ahmed and Kaj Tesink (editors) Expires 4/19/94[Page 18] Internet Draft ATM Management Objects October 19, 1993 _____________________________________________________________________ ATM interface:|(1)PDUs discarded for protocol | | | AAL5 CPCS | errors | MIB II |no | layers |(2)PDUs discarded for procedural | | | | or transmission errors | | | |(3)received/transmitted PDUs | | | _____________________________________________________________________ Virtual Connection Information: _____________________________________________________________________ Comments: |(1)port identifier of ingress | | | | end | | | Virtual |(2)port identifier of egress |ATM | | connection | end |MIB gr. 4 |no | information |(3)VPI or VPI/VCI value | | | are provided | of ingress VCL/VPL | | | for each |(4)VPI or VPI/VCI value of | | | direction | egress VCL/VPL | | | of the |(5)policing parameters of | | | connection. | ingress VCL/VPL | | | |(6)shaping parameters of | | | | egress VCL/VPL | | | |(7)QoS class of ingress | | | | VCL/VPL | | | |(8)VCC/VPC operational status | | | |(9)VCC/VPC administrative status | | | _____________________________________________________________________ Masuma Ahmed and Kaj Tesink (editors) Expires 4/19/94[Page 19] Internet Draft ATM Management Objects October 19, 1993 *The operational and administrative status of the ATM interface and the physical transmission type shall be supported by the interface table in MIB II. **The ILMI MIB contains local and end-to-end operational status of the VPC/VCC. However, it does not contain the administrative status of the local VPC/VCC. Also, the ILMI MIB contains policing parameters, shaping parameters and QoS class as local information and not as virtual connection information. The table 1 shows that the ILMI MIB supports most of the ATM functions that are supported by the ATM MIB groups 1, 4, and interface group in MIB II. The ILMI MIB contains the QoS Class, traffic policing and shaping parameters as the local interface information. This specification supports these functions in the virtual connection group to facilitate setting up or modifying virtual connections. This approach does not change the semantics of these variables, only the OBJECT IDENTIFIERs of these variables change. Masuma Ahmed and Kaj Tesink (editors) Expires 4/19/94[Page 20] Internet Draft ATM Management Objects October 19, 1993 10. Object Definitions ATM-MIB DEFINITIONS ::= BEGIN IMPORTS MODULE-IDENTITY, OBJECT-TYPE, experimental, Counter32, Integer32 FROM SNMPv2-SMI DisplayString, RowStatus FROM SNMPv2-TC MODULE-COMPLIANCE, OBJECT-GROUP FROM SNMPv2-CONF; atmMIB MODULE-IDENTITY LAST-UPDATED "9310191445Z" ORGANIZATION "IETF AToM MIB Working Group" CONTACT-INFO " Masuma Ahmed Bellcore 331 Newman Springs Road Red Bank, NJ 07701 Tel: 908-758-2515 Fax: 908-758-4192 E-mail: mxa@mail.bellcore.com Kaj Tesink Bellcore 331 Newman Springs Road Red Bank, NJ 07701 Tel: 908-758-5254 Fax: 908-758-4196 E-mail: kaj@cc.bellcore.com" DESCRIPTION "This is the MIB Module for ATM-related objects for managing ATM interfaces and ATM connections." ::= { experimental 41 } atmMIBObjects OBJECT IDENTIFIER ::= {atmMIB 1} Masuma Ahmed and Kaj Tesink (editors) Expires 4/19/94[Page 21] Internet Draft ATM Management Objects October 19, 1993 -- This ATM MIB Module consists of the following groups: -- (1) ATM Interface configuration group -- (2) ATM Interface DS3 PLCP group -- (3) ATM Interface TC Sublayer group -- (4) ATM VPC group -- (5) ATM VCC group IfIndex ::= TEXTUAL-CONVENTION STATUS current DESCRIPTION "The value of this object identifies the interface for which the entry contains management information. The value of this object for a particular interface has the same value as the ifIndex object, defined in RFC 1156 and RFC 1213, for the same interface." SYNTAX Integer32 Masuma Ahmed and Kaj Tesink (editors) Expires 4/19/94[Page 22] Internet Draft ATM Management Objects October 19, 1993 atmInterfaceTrafficEnforcementTypes OBJECT IDENTIFIER ::= {atmMIBObjects 1} -- The following values are defined for use as -- possible values of the type of Traffic Enforcement. -- It is assumed that the same algorithms will be -- used for traffic policing and shaping. -- Seven types of traffic enforcement have been -- specified so far by the ATM Forum UNI Specification, -- Draft 2.3, including one for the best effort traffic. -- The types of traffic policing and shaping atmInterfaceNoTrafficEnforcement OBJECT-IDENTITY STATUS current DESCRIPTION "This identifies the no ATM traffic enforcement type. Parameters 1, 2, 3, 4, and 5 are not used." ::= { atmInterfaceTrafficEnforcementTypes 1} atmInterfaceTrafficEnforcementType1 OBJECT-IDENTITY STATUS current DESCRIPTION "This identifies the ATM traffic enforcement type 1: Parameter 1: CLP=0+1 peak rate (cells per second) Parameter 2: not used Parameter 3: not used Parameter 4: not used Parameter 5: not used." ::= { atmInterfaceTrafficEnforcementTypes 2} atmInterfaceTrafficEnforcementType2 OBJECT-IDENTITY STATUS current DESCRIPTION "This identifies the ATM traffic enforcement type 2: Parameter 1: CLP=0 peak rate (cells per second) Parameter 2: CLP=0+1 peak rate (cells per second) Parameter 3: not used Parameter 4: not used Parameter 5: not used." ::= { atmInterfaceTrafficEnforcementTypes 3} atmInterfaceTrafficEnforcementType3 OBJECT-IDENTITY STATUS current DESCRIPTION "This identifies the ATM traffic enforcement type 3: Masuma Ahmed and Kaj Tesink (editors) Expires 4/19/94[Page 23] Internet Draft ATM Management Objects October 19, 1993 Parameter 1: CLP=0+1 peak rate (cells per second) Parameter 2: CLP=0 sustained rate (cells per second) Parameter 3: CLP=0 maximum burst size (cells) Parameter 4: not used Parameter 5: not used." ::= { atmInterfaceTrafficEnforcementTypes 4} atmInterfaceTrafficEnforcementType4 OBJECT-IDENTITY STATUS current DESCRIPTION "This identifies the ATM traffic enforcement type 4: Parameter 1: CLP=0 peak rate (cells per second) Parameter 2: CLP=0+1 peak rate (cells per second) Parameter 3: tagging (e.g., a value 1 may be used to indicate tagging) Parameter 4: not used Parameter 5: not used." ::= { atmInterfaceTrafficEnforcementTypes 5} atmInterfaceTrafficEnforcementType5 OBJECT-IDENTITY STATUS current DESCRIPTION "This identifies the ATM traffic enforcement type 5: Parameter 1: CLP=0+1 peak rate (cells per second) Parameter 2: CLP=0 sustained rate (cells per second) Parameter 3: CLP=0 maximum burst size (cells) Parameter 4: tagging (e.g., a value 1 may be used to indicate tagging) Parameter 5: not used." ::= { atmInterfaceTrafficEnforcementTypes 6} atmInterfaceTrafficEnforcementType6 OBJECT-IDENTITY STATUS current DESCRIPTION "This identifies the ATM traffic enforcement type 6: Parameter 1: CLP=0+1 peak rate (cells per second) Parameter 2: CLP=0+1 sustained rate (cells per second) Parameter 3: CLP=0+1 maximum burst size (cells) Parameter 4: not used Parameter 5: not used." ::= { atmInterfaceTrafficEnforcementTypes 7} atmInterfaceTrafficEnforcementType7 OBJECT-IDENTITY STATUS current DESCRIPTION Masuma Ahmed and Kaj Tesink (editors) Expires 4/19/94[Page 24] Internet Draft ATM Management Objects October 19, 1993 "This identifies the ATM traffic enforcement type 7: Parameter 1: CLP=0+1 peak rate (cells per second) Parameter 2: best effort traffic (e.g., a value 1 may be used to indicate best effort traffic) Parameter 3: not used Parameter 4: not used Parameter 5: not used." ::= { atmInterfaceTrafficEnforcementTypes 8} -- ATM Interface Configuration Parameters Group -- Implementation of this group is mandatory -- if providing ATM Interfaces. atmInterfaceConfTable OBJECT-TYPE SYNTAX SEQUENCE OF AtmInterfaceConfEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "This table contains ATM local interface configuration parameters and state variables, one entry per ATM interface port." ::= { atmMIBObjects 2 } atmInterfaceConfEntry OBJECT-TYPE SYNTAX AtmInterfaceConfEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "This list contains ATM interface configuration parameters and state variables." INDEX { atmInterfaceIndex } ::= { atmInterfaceConfTable 1} AtmInterfaceConfEntry ::= SEQUENCE { atmInterfaceIndex IfIndex, atmInterfaceMaxVpcs INTEGER, atmInterfaceMaxVccs INTEGER, atmInterfaceConfVpcs INTEGER, atmInterfaceConfVccs INTEGER, atmInterfaceMaxActiveVpiBits INTEGER, atmInterfaceMaxActiveVciBits INTEGER, atmInterfaceIlmiVpiVci Interger32 } Masuma Ahmed and Kaj Tesink (editors) Expires 4/19/94[Page 25] Internet Draft ATM Management Objects October 19, 1993 atmInterfaceIndex OBJECT-TYPE SYNTAX IfIndex MAX-ACCESS not-accessible STATUS current DESCRIPTION "The value of this object identifies the ATM port interface for which this entry contains management information." ::= { atmInterfaceConfEntry 1 } atmInterfaceMaxVpcs OBJECT-TYPE SYNTAX INTEGER (0..255) MAX-ACCESS read-only STATUS current DESCRIPTION "The maximum number of VPCs supported at this ATM interface." ::= { atmInterfaceConfEntry 2} atmInterfaceMaxVccs OBJECT-TYPE SYNTAX INTEGER (0..65535) MAX-ACCESS read-only STATUS current DESCRIPTION "The maximum number of VCCs supported at the ATM interface." ::= { atmInterfaceConfEntry 3} atmInterfaceConfVpcs OBJECT-TYPE SYNTAX INTEGER (0..255) MAX-ACCESS read-only STATUS current DESCRIPTION "The number of VPCs configured for use at this ATM interface." ::= { atmInterfaceConfEntry 4} atmInterfaceConfVccs OBJECT-TYPE SYNTAX INTEGER (0..65535) MAX-ACCESS read-only STATUS current DESCRIPTION "The number of VCCs configured for use at the ATM interface." ::= { atmInterfaceConfEntry 5} Masuma Ahmed and Kaj Tesink (editors) Expires 4/19/94[Page 26] Internet Draft ATM Management Objects October 19, 1993 atmInterfaceMaxActiveVpiBits OBJECT-TYPE SYNTAX INTEGER (0..8) MAX-ACCESS read-only STATUS current DESCRIPTION "The maximum number of active VPI bits configured for use at the ATM interface." ::= { atmInterfaceConfEntry 6} atmInterfaceMaxActiveVciBits OBJECT-TYPE SYNTAX INTEGER (0..16) MAX-ACCESS read-only STATUS current DESCRIPTION "The maximum number of active VCI bits configured for use at this ATM interface." ::= { atmInterfaceConfEntry 7} atmInterfaceIlmiVpiVci OBJECT-TYPE SYNTAX Integer32 MAX-ACCESS read-only STATUS current DESCRIPTION "The decimal value of the three octet VPI/VCI field that identifies the VCC supporting the ILMI at the ATM interface. If the value of this object is greater than 16777215 then the ILMI is not supported at the ATM interface. The default VPI/VCI values for ILMI are VPI=0 and VCI=16." ::= { atmInterfaceConfEntry 8} -- The ATM Interface DS3 PLCP Group -- Implementation of this group is mandatory -- if the DS3 PLCP is implemented. atmInterfaceDs3PlcpTable OBJECT-TYPE SYNTAX SEQUENCE OF AtmInterfaceDs3PlcpEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "This table contains ATM interface DS3 PLCP Masuma Ahmed and Kaj Tesink (editors) Expires 4/19/94[Page 27] Internet Draft ATM Management Objects October 19, 1993 parameters and state variables, one entry per ATM interface port." ::= { atmMIBObjects 3} atmInterfaceDs3PlcpEntry OBJECT-TYPE SYNTAX AtmInterfaceDs3PlcpEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "This list contains DS3 PLCP parameters and state variables at the ATM interface." INDEX {atmInterfaceDs3PlcpIndex } ::= { atmInterfaceDs3PlcpTable 1} AtmInterfaceDs3PlcpEntry ::= SEQUENCE { atmInterfaceDs3PlcpIndex IfIndex, atmInterfaceDs3PlcpSEFSs Counter32, atmInterfaceDs3PlcpAlarmState INTEGER, atmInterfaceDs3PlcpUASs Counter32 } atmInterfaceDs3PlcpIndex OBJECT-TYPE SYNTAX IfIndex MAX-ACCESS not-accessible STATUS current DESCRIPTION "The value of this object identifies the ATM interface port for which this entry contains management information and is the same as the atmInterfaceIndex." ::= { atmInterfaceDs3PlcpEntry 1} atmInterfaceDs3PlcpSEFSs OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "A DS3 Severely Errored Framing Second (SEFS) is a count of one-second intervals containing one or more SEF event." ::= { atmInterfaceDs3PlcpEntry 2} atmInterfaceDs3PlcpAlarmState OBJECT-TYPE SYNTAX INTEGER { noAlarm(1), Masuma Ahmed and Kaj Tesink (editors) Expires 4/19/94[Page 28] Internet Draft ATM Management Objects October 19, 1993 receivedFarEndAlarm(2), incomingLOF(3) } MAX-ACCESS read-only STATUS current DESCRIPTION "This variable indicates if there is an alarm present for the DS3 PLCP. The value receivedFarEndAlarm means that the DS3 PLCP has received an incoming Yellow Signal, the value incomingLOF means that the DS3 PLCP has declared a loss of frame (LOF) failure condition, and the value noAlarm means that there are no alarms present." ::= { atmInterfaceDs3PlcpEntry 3} atmInterfaceDs3PlcpUASs OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "The counter associated with the number of Unavailable Seconds encountered by the PLCP." ::= { atmInterfaceDs3PlcpEntry 4} -- The ATM Interface TC Sublayer Group -- Implementation of this group is mandatory -- if TC Sublayer is implemented. atmInterfaceTCTable OBJECT-TYPE SYNTAX SEQUENCE OF AtmInterfaceTCEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "This table contains ATM interface TC Sublayer parameters and state variables, one entry per ATM interface port." ::= { atmMIBObjects 4} atmInterfaceTCEntry OBJECT-TYPE SYNTAX AtmInterfaceTCEntry Masuma Ahmed and Kaj Tesink (editors) Expires 4/19/94[Page 29] Internet Draft ATM Management Objects October 19, 1993 MAX-ACCESS not-accessible STATUS current DESCRIPTION "This list contains TC Sublayer parameters and state variables at the ATM interface." INDEX {atmInterfaceTCIndex } ::= { atmInterfaceTCTable 1} AtmInterfaceTCEntry ::= SEQUENCE { atmInterfaceTCIndex IfIndex, atmInterfaceOCDEvents Counter32, atmInterfaceTCAlarmState INTEGER } atmInterfaceTCIndex OBJECT-TYPE SYNTAX IfIndex MAX-ACCESS not-accessible STATUS current DESCRIPTION "The value of this object identifies the ATM interface port for which this entry contains management information and is the same as the atmInterfaceIndex." ::= { atmInterfaceTCEntry 1} atmInterfaceOCDEvents OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "The number of times the Out of Cell Delineation (OCD) events occur. If seven consecutive ATM cells have Header Error Control (HEC) violations, an OCD event occurs. A high number of OCD events may indicate a problem with the TC Sublayer." ::= { atmInterfaceTCEntry 2} atmInterfaceTCAlarmState OBJECT-TYPE SYNTAX INTEGER { noAlarm(1), lcdFailure(2) } MAX-ACCESS read-only Masuma Ahmed and Kaj Tesink (editors) Expires 4/19/94[Page 30] Internet Draft ATM Management Objects October 19, 1993 STATUS current DESCRIPTION "This variable indicates if there is an alarm present for the TC Sublayer. The value lcdFailure indicates that a Loss of Cell Delineation (LCD) failure state has been declared for the TC Sublayer." ::= { atmInterfaceTCEntry 3} -- ATM Virtual Path Connection (VPC) Group -- Implementation of this group is mandatory if providing -- an ATM Virtual Path Connection at an ATM interface. -- This group provides configuration information of the -- VPC segment. -- Note: This group is under review. -- See IETF Amsterdam AToM MIB WG meeting report. atmVPConnectionTable OBJECT-TYPE SYNTAX SEQUENCE OF AtmVPConnectionTableEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "This table contains ATM VPC configuration and performance parameters and state variables. Each entry represents a unidirectional traffic flow. Multiple entries are necessary to represent a bidirectional and multipoint connections." ::= { atmMIBObjects 7 } atmVPConnectionTableEntry OBJECT-TYPE SYNTAX AtmVPConnectionTableEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "A unidirectional traffic flow." INDEX {atmVPConnectionIngressPort, atmVPConnectionIngressVpi, atmVPConnectionEgressPort, atmVPConnectionEgressVpi } ::= { atmVPConnectionTable 1} AtmVPConnectionTableEntry ::= Masuma Ahmed and Kaj Tesink (editors) Expires 4/19/94[Page 31] Internet Draft ATM Management Objects October 19, 1993 SEQUENCE { atmVPConnectionTableEntryStatus RowStatus, atmVPConnectionIngressPort IfIndex, atmVPConnectionIngressVpi INTEGER, atmVPConnectionEgressPort IfIndex, atmVPConnectionEgressVpi INTEGER, atmVPConnectionOperStatus INTEGER, atmVPConnectionAdminStatus INTEGER, atmVPConnectionTrafficShaperType OBJECT IDENTIFIER, atmVPConnectionTrafficShaperParam1 INTEGER, atmVPConnectionTrafficShaperParam2 INTEGER, atmVPConnectionTrafficShaperParam3 INTEGER, atmVPConnectionTrafficShaperParam4 INTEGER, atmVPConnectionTrafficShaperParam5 INTEGER, atmVPConnectionTrafficPolicerType OBJECT IDENTIFIER, atmVPConnectionTrafficPolicerParam1 INTEGER, atmVPConnectionTrafficPolicerParam2 INTEGER, atmVPConnectionTrafficPolicerParam3 INTEGER, atmVPConnectionTrafficPolicerParam4 INTEGER, atmVPConnectionTrafficPolicerParam5 INTEGER, atmVPConnectionQoSClass INTEGER } atmVPConnectionTableEntryStatus OBJECT-TYPE SYNTAX RowStatus MAX-ACCESS read-create STATUS current DESCRIPTION "The status column used for creating, modifying, and deleting instances of the supplemental objects in the conceptual row of the virtual connection table." DEFVAL { active } ::= { atmVPConnectionTableEntry 1 } atmVPConnectionIngressPort OBJECT-TYPE SYNTAX IfIndex MAX-ACCESS not-accessible STATUS current DESCRIPTION "The value of this object identifies the ingress ATM port of the VPC segment." ::= { atmVPConnectionTableEntry 2 } atmVPConnectionIngressVpi OBJECT-TYPE Masuma Ahmed and Kaj Tesink (editors) Expires 4/19/94[Page 32] Internet Draft ATM Management Objects October 19, 1993 SYNTAX INTEGER (1..255) MAX-ACCESS not-accessible STATUS current DESCRIPTION "The VPI value at the ingress port of the traffic flow. The VPI=0 is reserved for VCC. The maximum VPI value cannot exceed the number allowed by the atmInterfaceMaxVpiBits specified for the ingress ATM port." ::= { atmVPConnectionTableEntry 3 } atmVPConnectionEgressPort OBJECT-TYPE SYNTAX IfIndex MAX-ACCESS not-accessible STATUS current DESCRIPTION "The value of this object identifies the ingress ATM port of the VPC segment." ::= { atmVPConnectionTableEntry 4 } atmVPConnectionEgressVpi OBJECT-TYPE SYNTAX INTEGER (1..255) MAX-ACCESS not-accessible STATUS current DESCRIPTION "The VPI value at the egress port of the traffic flow. The VPI=0 is reserved for VCC. The maximum VPI value cannot exceed the number supported by the atmInterfaceMaxVpiBits specified for the egress ATM port." ::= { atmVPConnectionTableEntry 5 } atmVPConnectionOperStatus OBJECT-TYPE SYNTAX INTEGER { up(1), down(2) } MAX-ACCESS read-only STATUS current DESCRIPTION "This object indicates the operational status of the VPC, i.e., whether the managed segment of the VPC is up or down. Masuma Ahmed and Kaj Tesink (editors) Expires 4/19/94[Page 33] Internet Draft ATM Management Objects October 19, 1993 In the down state, no cells can be passed across this segment of the VPC." ::= { atmVPConnectionTableEntry 6 } atmVPConnectionAdminStatus OBJECT-TYPE SYNTAX INTEGER { up(1), down(2) } MAX-ACCESS read-write STATUS current DESCRIPTION "This object indicates the desired status of the VPC, i.e., whether the managed segment of the VPC is up or down. In the down state, no cells can be passed across this segment of the VPC." ::= { atmVPConnectionTableEntry 7 } atmVPConnectionTrafficShaperType OBJECT-TYPE SYNTAX OBJECT IDENTIFIER MAX-ACCESS read-write STATUS current DESCRIPTION "The value of this object identifies the type of traffic shaping algorithm active on the egress of the traffic flow. The type may indicate no traffic shaping or traffic shaping with one or more parameters. These parameters are specified as a parameter vector, in the corresponding instances of the objects: atmVPConnectionTrafficShaperParam1 atmVPConnectionTrafficShaperParam2 atmVPConnectionTrafficShaperParam3 atmVPConnectionTrafficShaperParam4 atmVPConnectionTrafficShaperParam5." ::= { atmVPConnectionTableEntry 8} atmVPConnectionTrafficShaperParam1 OBJECT-TYPE SYNTAX INTEGER (0..2147483647) MAX-ACCESS read-write STATUS current DESCRIPTION "The first parameter of the traffic shaper for this VPC segment used according to the value of Masuma Ahmed and Kaj Tesink (editors) Expires 4/19/94[Page 34] Internet Draft ATM Management Objects October 19, 1993 atmVPConnectionTrafficShaperType." ::= { atmVPConnectionTableEntry 9} atmVPConnectionTrafficShaperParam2 OBJECT-TYPE SYNTAX INTEGER (0..2147483647) MAX-ACCESS read-write STATUS current DESCRIPTION "The second parameter of the traffic shaper for this VPC segment used according to the value of atmVPConnectionTrafficShaperType." ::= { atmVPConnectionTableEntry 10} atmVPConnectionTrafficShaperParam3 OBJECT-TYPE SYNTAX INTEGER (0..2147483647) MAX-ACCESS read-write STATUS current DESCRIPTION "The third parameter of the traffic shaper for this VPC segment used according to the value of atmVPConnectionTrafficShaperType." ::= { atmVPConnectionTableEntry 11} atmVPConnectionTrafficShaperParam4 OBJECT-TYPE SYNTAX INTEGER (0..2147483647) MAX-ACCESS read-write STATUS current DESCRIPTION "The fourth parameter of the traffic shaper for this VPC segment used according to the value of atmVPConnectionTrafficShaperType." ::= { atmVPConnectionTableEntry 12} atmVPConnectionTrafficShaperParam5 OBJECT-TYPE SYNTAX INTEGER (0..2147483647) MAX-ACCESS read-write STATUS current DESCRIPTION "The fifth parameter of the traffic shaper for this VPC segment used according to the value of atmVPConnectionTrafficShaperType." ::= { atmVPConnectionTableEntry 13} atmVPConnectionTrafficPolicerType OBJECT-TYPE SYNTAX OBJECT IDENTIFIER Masuma Ahmed and Kaj Tesink (editors) Expires 4/19/94[Page 35] Internet Draft ATM Management Objects October 19, 1993 MAX-ACCESS read-write STATUS current DESCRIPTION "The value of this object identifies the type of traffic policing algorithm active on the ingress of this traffic flow. The type may indicate no traffic policing or traffic policing with one or more parameters. These parameters are specified as a parameter vector, in the corresponding instances of the objects: atmVPConnectionTrafficPolicerParam1 atmVPConnectionTrafficPolicerParam2 atmVPConnectionTrafficPolicerParam3 atmVPConnectionTrafficPolicerParam4 atmVPConnectionTrafficPolicerParam5." ::= { atmVPConnectionTableEntry 14} atmVPConnectionTrafficPolicerParam1 OBJECT-TYPE SYNTAX INTEGER (0..2147483647) MAX-ACCESS read-write STATUS current DESCRIPTION "The first parameter of the traffic policer for this VPC segment used according to the value of atmVPConnectionTrafficPolicerType." ::= { atmVPConnectionTableEntry 15} atmVPConnectionTrafficPolicerParam2 OBJECT-TYPE SYNTAX INTEGER (0..2147483647) MAX-ACCESS read-write STATUS current DESCRIPTION "The second parameter of the traffic policing for this VPC segment used according to the value of atmVPConnectionTrafficPolicerType." ::= { atmVPConnectionTableEntry 16} atmVPConnectionTrafficPolicerParam3 OBJECT-TYPE SYNTAX INTEGER (0..2147483647) MAX-ACCESS read-write STATUS current DESCRIPTION "The third parameter of the traffic policer for this VPC segment used according to the value of Masuma Ahmed and Kaj Tesink (editors) Expires 4/19/94[Page 36] Internet Draft ATM Management Objects October 19, 1993 atmVPConnectionTrafficPolicerType." ::= { atmVPConnectionTableEntry 17} atmVPConnectionTrafficPolicerParam4 OBJECT-TYPE SYNTAX INTEGER (0..2147483647) MAX-ACCESS read-write STATUS current DESCRIPTION "The fourth parameter of the traffic policing algorithm for this VPC segment used according to the value of atmVPConnectionTrafficPolicerType." ::= { atmVPConnectionTableEntry 18} atmVPConnectionTrafficPolicerParam5 OBJECT-TYPE SYNTAX INTEGER (0..2147483647) MAX-ACCESS read-write STATUS current DESCRIPTION "The fifth parameter of the traffic policing algorithm for this VPC segment used according to the value of atmVPConnectionTrafficPolicerType." ::= { atmVPConnectionTableEntry 19} atmVPConnectionQoSClass OBJECT-TYPE SYNTAX INTEGER { unspecified(5), class1(1), class2(2), class3(3), class4(4) } MAX-ACCESS read-write STATUS current DESCRIPTION "The value of this object identifies the QoS Class associated with this traffic flow. Four QoS classes have been specified in the ATM Forum UNI Specification Document, Draft 2.3 to support service class A (constant bit rate video and circuit emulation), service class B (variable bit rate video/audio), service class C (connection-oriented data) and service class D (connectionless data). The value unspecified indicates that this VPC has Masuma Ahmed and Kaj Tesink (editors) Expires 4/19/94[Page 37] Internet Draft ATM Management Objects October 19, 1993 unspecified QoS Class." ::= {atmVPConnectionTableEntry 20} -- ATM Virtual Channel Connection (VCC) Group -- Implementation of this group is mandatory if providing -- an ATM Virtual Channel Connections at an ATM interface. -- This group provides configuration information of the -- VCC segment information. atmVCConnectionTable OBJECT-TYPE SYNTAX SEQUENCE OF AtmVCConnectionTableEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "This table contains ATM VCC configuration and performance parameters and state variables. Each entry represents a unidirectional traffic flow. Multiple entries are necessary to represent a bidirectional and multipoint connections." ::= { atmMIBObjects 8 } atmVCConnectionTableEntry OBJECT-TYPE SYNTAX AtmVCConnectionTableEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "A unidirectional traffic flow." INDEX {atmVCConnectionIngressPort, atmVCConnectionIngressVpi, atmVCConnectionIngressVci, atmVCConnectionEgressPort, atmVCConnectionEgressVpi, atmVCConnectionEgressVci } ::= { atmVCConnectionTable 1} AtmVCConnectionTableEntry ::= SEQUENCE { atmVCConnectionTableEntryStatus RowStatus, atmVCConnectionIngressPort IfIndex, atmVCConnectionIngressVpi INTEGER, atmVCConnectionIngressVci INTEGER, atmVCConnectionEgressPort IfIndex, atmVCConnectionEgressVpi INTEGER, Masuma Ahmed and Kaj Tesink (editors) Expires 4/19/94[Page 38] Internet Draft ATM Management Objects October 19, 1993 atmVCConnectionEgressVci INTEGER, atmVCConnectionOperStatus INTEGER, atmVCConnectionAdminStatus INTEGER, atmVCConnectionTrafficShaperType OBJECT IDENTIFIER, atmVCConnectionTrafficShaperParam1 INTEGER, atmVCConnectionTrafficShaperParam2 INTEGER, atmVCConnectionTrafficShaperParam3 INTEGER, atmVCConnectionTrafficShaperParam4 INTEGER, atmVCConnectionTrafficShaperParam5 INTEGER, atmVCConnectionTrafficPolicerType OBJECT IDENTIFIER, atmVCConnectionTrafficPolicerParam1 INTEGER, atmVCConnectionTrafficPolicerParam2 INTEGER, atmVCConnectionTrafficPolicerParam3 INTEGER, atmVCConnectionTrafficPolicerParam4 INTEGER, atmVCConnectionTrafficPolicerParam5 INTEGER, atmVCConnectionQoSClass INTEGER } atmVCConnectionTableEntryStatus OBJECT-TYPE SYNTAX RowStatus MAX-ACCESS read-create STATUS current DESCRIPTION "The status column used for creating, modifying, and deleting instances of the supplemental objects of the conceptual row in the virtual channel connection table." DEFVAL { active } ::= { atmVCConnectionTableEntry 1 } atmVCConnectionIngressPort OBJECT-TYPE SYNTAX IfIndex MAX-ACCESS not-accessible STATUS current DESCRIPTION "The value of this object identifies the ingress ATM port of the VCC segment." ::= { atmVCConnectionTableEntry 2 } atmVCConnectionIngressVpi OBJECT-TYPE SYNTAX INTEGER (0..255) MAX-ACCESS not-accessible STATUS current DESCRIPTION "The VPI value at the ingress Masuma Ahmed and Kaj Tesink (editors) Expires 4/19/94[Page 39] Internet Draft ATM Management Objects October 19, 1993 port of the traffic flow. The maximum VPI value cannot exceed the number supported by the atmInterfaceMaxVpiBits at the ingress ATM port." ::= { atmVCConnectionTableEntry 3 } atmVCConnectionIngressVci OBJECT-TYPE SYNTAX INTEGER (32..65535) MAX-ACCESS not-accessible STATUS current DESCRIPTION "The VCI value at the ingress port of the traffic flow. The VCI values from 0 to 31 are reserved. The maximum VCI value cannot exceed the number supported by the atmInterfaceMaxVciBits specified for the ingress ATM port." ::= { atmVCConnectionTableEntry 4 } atmVCConnectionEgressPort OBJECT-TYPE SYNTAX IfIndex MAX-ACCESS not-accessible STATUS current DESCRIPTION "The value of this object identifies the ingress ATM port of the VCC segment." ::= { atmVCConnectionTableEntry 5 } atmVCConnectionEgressVpi OBJECT-TYPE SYNTAX INTEGER (0..255) MAX-ACCESS not-accessible STATUS current DESCRIPTION "The VPI value at the egress port of the traffic flow. The maximum VPI value cannot exceed the number supported by the atmInterfaceMaxVpiBits at the egress ATM port." ::= { atmVCConnectionTableEntry 6 } atmVCConnectionEgressVci OBJECT-TYPE SYNTAX INTEGER (32..65535) MAX-ACCESS not-accessible STATUS current DESCRIPTION Masuma Ahmed and Kaj Tesink (editors) Expires 4/19/94[Page 40] Internet Draft ATM Management Objects October 19, 1993 "The VCI value at the egress port of the traffic flow. The VCI values from 0 to 31 are reserved. The maximum VCI value cannot exceed the number supported by the atmInterfaceMaxVciBits specified for the egress ATM port." ::= { atmVCConnectionTableEntry 7 } atmVCConnectionOperStatus OBJECT-TYPE SYNTAX INTEGER { up(1), down(2) } MAX-ACCESS read-only STATUS current DESCRIPTION "This object indicates the operational status of the VCC, i.e., whether the managed VCC segment is up or down. In the down state, no cells can be passed across this VCC segment." ::= { atmVCConnectionTableEntry 8 } atmVCConnectionAdminStatus OBJECT-TYPE SYNTAX INTEGER { up(1), down(2) } MAX-ACCESS read-write STATUS current DESCRIPTION "This object indicates the desired status of the VCC, i.e., whether the managed VCC segment is up or down. In the down state, no cells can be passed across this VCC segment." ::= { atmVCConnectionTableEntry 9 } atmVCConnectionTrafficShaperType OBJECT-TYPE SYNTAX OBJECT IDENTIFIER MAX-ACCESS read-write STATUS current DESCRIPTION "The value of this object identifies the type of traffic shaping algorithm active on the egress of the traffic flow. The type may indicate no Masuma Ahmed and Kaj Tesink (editors) Expires 4/19/94[Page 41] Internet Draft ATM Management Objects October 19, 1993 traffic shaping or traffic shaping with one or more parameters. These parameters are specified as a parameter vector, in the corresponding instances of the objects: atmVCConnectionTrafficShaperParam1 atmVCConnectionTrafficShaperParam2 atmVCConnectionTrafficShaperParam3 atmVCConnectionTrafficShaperParam4 atmVCConnectionTrafficShaperParam5." ::= { atmVCConnectionTableEntry 10} atmVCConnectionTrafficShaperParam1 OBJECT-TYPE SYNTAX INTEGER (0..2147483647) MAX-ACCESS read-write STATUS current DESCRIPTION "The first parameter of the traffic shaper for this VCC segment used according to the value of atmVPConnectionTrafficShaperType." ::= { atmVCConnectionTableEntry 11} atmVCConnectionTrafficShaperParam2 OBJECT-TYPE SYNTAX INTEGER (0..2147483647) MAX-ACCESS read-write STATUS current DESCRIPTION "The second parameter of the traffic shaper for this VCC segment used according to the value of atmVPConnectionTrafficShaperType." ::= { atmVCConnectionTableEntry 12} atmVCConnectionTrafficShaperParam3 OBJECT-TYPE SYNTAX INTEGER (0..2147483647) MAX-ACCESS read-write STATUS current DESCRIPTION "The third parameter of the traffic shaper for this VCC segment used according to the value of atmVPConnectionTrafficShaperType." ::= { atmVCConnectionTableEntry 13} atmVCConnectionTrafficShaperParam4 OBJECT-TYPE SYNTAX INTEGER (0..2147483647) MAX-ACCESS read-write STATUS current Masuma Ahmed and Kaj Tesink (editors) Expires 4/19/94[Page 42] Internet Draft ATM Management Objects October 19, 1993 DESCRIPTION "The fourth parameter of the traffic shaper for this VCC segment used according to the value of atmVCConnectionTrafficShaperType." ::= { atmVCConnectionTableEntry 14} atmVCConnectionTrafficShaperParam5 OBJECT-TYPE SYNTAX INTEGER (0..2147483647) MAX-ACCESS read-write STATUS current DESCRIPTION "The fifth parameter of the traffic shaper for this VCC segment used according to the value of atmVCConnectionTrafficShaperType." ::= { atmVCConnectionTableEntry 15} atmVCConnectionTrafficPolicerType OBJECT-TYPE SYNTAX OBJECT IDENTIFIER MAX-ACCESS read-write STATUS current DESCRIPTION "The value of this object identifies the type of traffic policing algorithm active on the ingress of the traffic flow. The type may indicate no traffic policing or traffic policing with one or more parameters. These parameters are specified as a parameter vector, in the corresponding instances of the objects: atmVCConnectionTrafficPolicerParam1 atmVCConnectionTrafficPolicerParam2 atmVCConnectionTrafficPolicerParam3 atmVCConnectionTrafficPolicerParam4 atmVCConnectionTrafficPolicerParam5." ::= { atmVCConnectionTableEntry 16} atmVCConnectionTrafficPolicerParam1 OBJECT-TYPE SYNTAX INTEGER (0..2147483647) MAX-ACCESS read-write STATUS current DESCRIPTION "The first parameter of the traffic policer for this VCC segment used according to the value of atmVCConnectionTrafficPolicerType." ::= { atmVCConnectionTableEntry 17} Masuma Ahmed and Kaj Tesink (editors) Expires 4/19/94[Page 43] Internet Draft ATM Management Objects October 19, 1993 atmVCConnectionTrafficPolicerParam2 OBJECT-TYPE SYNTAX INTEGER (0..2147483647) MAX-ACCESS read-write STATUS current DESCRIPTION "The second parameter of the traffic policing for this VCC segment used according to the value of atmVCConnectionTrafficPolicerType." ::= { atmVCConnectionTableEntry 18} atmVCConnectionTrafficPolicerParam3 OBJECT-TYPE SYNTAX INTEGER (0..2147483647) MAX-ACCESS read-write STATUS current DESCRIPTION "The third parameter of the traffic policer for this VCC segment used according to the value of atmVCConnectionTrafficPolicerType." ::= { atmVCConnectionTableEntry 19} atmVCConnectionTrafficPolicerParam4 OBJECT-TYPE SYNTAX INTEGER (0..2147483647) MAX-ACCESS read-write STATUS current DESCRIPTION "The fourth parameter of the traffic policing algorithm for this VCC segment used according to the value of atmVCConnectionTrafficPolicerType." ::= { atmVCConnectionTableEntry 20} atmVCConnectionTrafficPolicerParam5 OBJECT-TYPE SYNTAX INTEGER (0..2147483647) MAX-ACCESS read-write STATUS current DESCRIPTION "The fifth parameter of the traffic policing algorithm for this VCC segment used according to the value of atmVCConnectionTrafficPolicerType." ::= { atmVCConnectionTableEntry 21} atmVCConnectionQoSClass OBJECT-TYPE SYNTAX INTEGER { unspecified(5), class1(1), Masuma Ahmed and Kaj Tesink (editors) Expires 4/19/94[Page 44] Internet Draft ATM Management Objects October 19, 1993 class2(2), class3(3), class4(4) } MAX-ACCESS read-write STATUS current DESCRIPTION "The value of this object identifies the QoS Class associated with the originating VCL of the VCC. Four QoS classes have been specified in the ATM Forum UNI Specification Document, Draft 2.3 to support service class A (constant bit rate video and circuit emulation), service class B (variable bit rate video/audio), service class C (connection-oriented data) and service class D (connectionless data). The value unspecified indicates that this VCC has unspecified QoS Class." ::= {atmVCConnectionTableEntry 22} Masuma Ahmed and Kaj Tesink (editors) Expires 4/19/94[Page 45] Internet Draft ATM Management Objects October 19, 1993 -- Conformance Information atmMIBConformance OBJECT IDENTIFIER ::= { atmMIB 2 } atmMIBGroups OBJECT IDENTIFIER ::= { atmMIBConformance 1 } atmMIBCompliances OBJECT IDENTIFIER ::= { atmMIBConformance 2 } -- Compliance Statements atmMIBCompliance MODULE-COMPLIANCE STATUS current DESCRIPTION "The compliance statement for SNMP entities which have ATM interfaces." MODULE -- this module MANDATORY-GROUPS { atmInterfaceConfGroup } GROUP atmInterfaceDs3PlcpGroup DESCRIPTION "This group is mandatory only for those ATM interfaces which implement the DS3 PLCP layer." GROUP atmInterfaceTCGroup DESCRIPTION "This group is mandatory only for those ATM interfaces which implement the TC Sublayer." GROUP atmInterfaceVpcGroup DESCRIPTION "This group is mandatory only for those ATM interfaces which implement ATM VPC segments." GROUP atmInterfaceVccGroup DESCRIPTION "This group is mandatory only for those ATM interfaces which implement ATM VCC segments." ::= { atmMIBCompliances 1 } -- Units of Conformance Masuma Ahmed and Kaj Tesink (editors) Expires 4/19/94[Page 46] Internet Draft ATM Management Objects October 19, 1993 atmInterfaceConfGroup OBJECT-GROUP OBJECTS {atmInterfaceMaxVpcs, atmInterfaceMaxVccs, atmInterfaceConfVpcs, atmInterfaceConfVccs, atmInterfaceMaxActiveVpiBits, atmInterfaceMaxActiveVciBits, atmInterfaceIlmiVpiVci } STATUS current DESCRIPTION "A collection of objects providing configuration information about an ATM interface." ::= { atmMIBGroups 1 } atmInterfaceDs3PlcpGroup OBJECT-GROUP OBJECTS {atmInterfaceDs3PlcpSEFSs, atmInterfaceDs3PlcpAlarmState, atmInterfaceDs3PlcpUASs} STATUS current DESCRIPTION "A collection of objects providing information about DS3 PLCP layer at an ATM interface." ::= { atmMIBGroups 2 } atmInterfaceTCGroup OBJECT-GROUP OBJECTS { atmInterfaceOCDEvents, atmInterfaceTCAlarmState } STATUS current DESCRIPTION "A collection of objects providing information about the TC sublayer at an ATM interface." ::= { atmMIBGroups 3 } atmInterfaceVpcGroup OBJECT-GROUP OBJECTS {atmVPConnectionTableEntryStatus, atmVPConnectionOperStatus, atmVPConnectionAdminStatus, atmVPConnectionTrafficShaperType, atmVPConnectionTrafficShaperParam1, atmVPConnectionTrafficShaperParam2, atmVPConnectionTrafficShaperParam3, atmVPConnectionTrafficShaperParam4, atmVPConnectionTrafficShaperParam5, atmVPConnectionTrafficPolicerType, atmVPConnectionTrafficPolicerParam1, atmVPConnectionTrafficPolicerParam2, Masuma Ahmed and Kaj Tesink (editors) Expires 4/19/94[Page 47] Internet Draft ATM Management Objects October 19, 1993 atmVPConnectionTrafficPolicerParam3, atmVPConnectionTrafficPolicerParam4, atmVPConnectionTrafficPolicerParam5, atmVPConnectionQoSClass } STATUS current DESCRIPTION "A collection of objects providing information about the VPC at an ATM interface." ::= { atmMIBGroups 4 } atmInterfaceVccGroup OBJECT-GROUP OBJECTS {atmVCConnectionTableEntryStatus, atmVCConnectionOperStatus, atmVCConnectionAdminStatus, atmVCConnectionTrafficShaperType, atmVCConnectionTrafficShaperParam1, atmVCConnectionTrafficShaperParam2, atmVCConnectionTrafficShaperParam3, atmVCConnectionTrafficShaperParam4, atmVCConnectionTrafficShaperParam5, atmVCConnectionTrafficPolicerType, atmVCConnectionTrafficPolicerParam1, atmVCConnectionTrafficPolicerParam2, atmVCConnectionTrafficPolicerParam3, atmVCConnectionTrafficPolicerParam4, atmVCConnectionTrafficPolicerParam5, atmVCConnectionQoSClass } STATUS current DESCRIPTION "A collection of objects providing information about the VCC at an ATM interface." ::= { atmMIBGroups 5 } END Masuma Ahmed and Kaj Tesink (editors) Expires 4/19/94[Page 48] Internet Draft ATM Management Objects October 19, 1993 11. Acknowledgments This memo is the result of the work of the AToMMIB Working Group. Masuma Ahmed and Kaj Tesink (editors) Expires 4/19/94[Page 49] Internet Draft ATM Management Objects October 19, 1993 12. References [1] K. McCloghrie and M.T. Rose, Management Information Base for Network Management of TCP/IP-based internets, Internet Working Group Request for Comments 1156. Network Information Center, SRI International, Menlo Park, California, (May 1990). [2] M.T. Rose (editor), Management Information Base for Network Management of TCP/IP-based internets, Internet Working Group Request for Comments 1213. Network Information Center, SRI International, Menlo Park, California, (March 1991). [3] Information processing systems - Open Systems Interconnection - Specification of Abstract Syntax Notation One (ASN.1), International Organization for Standardization. International Standard 8824, (December 1987). [4] Information processing systems - Open Systems Interconnection - Specification of Basic Encoding Rules for Abstract Syntax Notation One (ASN.1), International Organization for Standardization. International Standard 8825, (December, 1987). [5] K. McCloghrie and F. Kastenholz, Evolution of Interfaces Group of MIB-II, Internet Draft, September 1993. [6] T. Cox and K. Tesink, Definitions of Managed Objects for SIP Interface Type, RFC1304, Network Information Center, SRI International, Menlo Park, California, February 1992. [7] J. Case, K. McCloghrie, M. Rose, and S. Waldbusser, Structure of Management Information for SNMPv2, RFC1442, Network Information Center, SRI International, Menlo Park, California, April 1993. [8] J. Case, K. McCloghrie, M. Rose, and S. Waldbusser, Textual Conventions for SNMPv2, RFC1443, Network Information Center, SRI International, Menlo Park, California, April 1993. [9] J. Case, K. McCloghrie, M. Rose, and S. Waldbusser, Conformance Statements for SNMPv2, RFC1444, Network Masuma Ahmed and Kaj Tesink (editors) Expires 4/19/94[Page 50] Internet Draft ATM Management Objects October 19, 1993 Information Center, SRI International, Menlo Park, California, April 1993. [10] J. Galvin and K. McCloghrie, Administrative Model for SNMPv2, RFC1445, Network Information Center, SRI International, Menlo Park, California, April 1993. [11] J. Case, K. McCloghrie, M. Rose, and S. Waldbusser, Protocol Operations for SNMPv2, RFC1448, Network Information Center, SRI International, Menlo Park, California, April 1993. [12] ATM Forum UNI Specification Document, Version 3, September 1993. Masuma Ahmed and Kaj Tesink (editors) Expires 4/19/94[Page 51] Internet Draft ATM Management Objects October 19, 1993 13. Security Considerations Security issues are not discussed in this memo. 14. Authors' Addresses Masuma Ahmed Bell Communications Research Room 1F-217 331 Newman Springs Road P.O. Box 7020 Red Bank, NJ 07701-7020 Phone: (908) 758-2515 EMail: mxa@mail.bellcore.com Kaj Tesink Bell Communications Research Room 1A-427 331 Newman Springs Road P.O. Box 7020 Red Bank, NJ 07701-7020 Phone: (908) 758-5254 EMail: kaj@cc.bellcore.com Masuma Ahmed and Kaj Tesink (editors) Expires 4/19/94[Page 52] Internet Draft ATM Management Objects October 19, 1993 Table of Contents 1 Status of this Memo ................................... 1 2 Abstract .............................................. 2 3 Change Log ............................................ 2 4 The SNMPv2 Network Management Framework ............... 4 5 Objects ............................................... 5 5.1 Format of Definitions ............................... 5 6 ATM Terminology ....................................... 6 6.1 VCL/VPL and VCC/VPC ................................. 6 6.2 PVC and SVC ......................................... 8 6.3 Traffic Management Parameters ....................... 8 6.3.1 Traffic Policing and Traffic Shaping Parameters .................................................... 8 6.3.2 Cell Loss Priority ................................ 9 6.3.3 QoS Class ......................................... 9 7 Overview .............................................. 9 7.1 Background .......................................... 9 7.2 Structure of the MIB ................................ 10 7.3 ATM Interface Configuration Group ................... 10 7.4 ATM Interface DS3 PLCP and TC Layer Groups .......... 11 7.5 ATM Virtual Connection Segment Groups ............... 11 7.5.1 Introduction ...................................... 11 7.5.2 Virtual Connection Identifiers at Ingress and Egress ............................................. 13 7.5.3 Virtual Connection Characterization ............... 13 7.5.4 Sets .............................................. 14 7.5.5 Virtual Connection Association with Interface Addresses .......................................... 15 7.5.6 Management of an End-to-End Virtual Connection .................................................... 15 8 Application of MIB II to ATM .......................... 15 8.1 The System Group .................................... 15 8.2 The Interface Group ................................. 15 8.2.1 Support of the ATM Cell Layer by ifTable .......... 16 8.2.2 Support of the AAL3/4 by RFC 1304 ................. 17 8.2.3 Support of the AAL5 by ifTable and the ATM MIB .................................................... 17 9 ILMI MIB and The ATM Managed Objects .................. 17 10 Object Definitions ................................... 21 11 Acknowledgments ...................................... 49 12 References ........................................... 50 13 Security Considerations .............................. 52 14 Authors' Addresses ................................... 52 Masuma Ahmed and Kaj Tesink (editors) Expires 4/19/94[Page 53] Internet Draft ATM Management Objects October 19, 1993 Masuma Ahmed and Kaj Tesink (editors) Expires 4/19/94[Page 54]